2013-02-19 - 5807 - Service Request - RFC Destination server update in NEQ #MMPPSupport

2012-02-19 - 5807 - Service Request - RFC Destination server update in NEQ

Problem Summary

---

MRP Run batch job is scheduled in SM37 in NEQ and it failed after running for a while.

Admin Info

---

Purpose	RFC Destination server update in NEQ
Requested by	Saravanan Lakshmanan
Issue Date	02-19-2013
Resolved by	Adithya
Resolved Date	02-19-2013
Document Status	Complete

Detailed Problem Description

(Include Screen Shots if required )

---

When MRP run is carried out, system was throwing an error. If a back ground job is scheduled in SM37 the job is failed.

Solution Analysis and Recommendations

(Include Screen Shots if required)

---

It was observed that, the MRP run is failed in both back ground (scheduling a job in SM37) and foreground (MD01).

It was found that no destination server have been entered in customizing or none of the the destinations (application server) entered are active.
In Customizing for MRP, you define the logical destinations (servers) to be used for parallel processing.

As NEQ is copied with NEP data on 26th December 2012, the server entered for parallel MRP run is also copied as it is in NEP,
It was observed that servers NECNEPA1_NEP_11 and NECNEPA1_NEP_12 were setup in NEQ as it is copied from NEP.

necahx01_NEQ_02 must be the destination for parallel processing in NEQ

To find the location of the server in customizing: SPRO --> Production --> MRP --> Define Parller Pocessing in MRP

Resolution

---

Communicated to client that server ''necahx01_NEQ_02'' has to be updated in: SPRO --> Production --> MRP --> Define Parller Pocessing in MRP

Release Information

---

Provide link here to Release Notes if Technical Objects were changed